Conversation
…ssion management, and participant event processing. Update Go module version and dependencies. Add README documentation for the coordinator and its components.
…entity management, and session handling. Introduce badger storage for session artifacts and implement NATS messaging topics for peer communication.
…mes, including YAML configuration files. Introduce a coordinator client for key generation requests and enhance logging throughout the runtime processes. Update .gitignore to include new configuration files.
…ntity handling. Introduce validation and default application for configuration parameters. Implement transport abstraction for NATS messaging, improving session management and peer communication. Add new interfaces for storage management of preparams, shares, and session artifacts.
…ludes source file name. Update Error function to skip an additional stack frame for accurate caller reporting.
…. Introduce Relay interface for unified messaging operations, enhancing configuration management and session handling. Update runtime to utilize relay abstraction, improving flexibility and maintainability.
…duce configuration management for relay settings, including credential loading and topic mapping. Implement runtime for handling MQTT and NATS messaging, enhancing session management and peer communication.
…type. Enhance NATS relay initialization with TLS support and credential management. Update validation logic to ensure required fields are checked for NATS relay provider.
…introduce ECDSA preparams handling. Update .gitignore to include new configuration files and dependencies. Improve session management with default values for configuration parameters.
… initialization and improving key generation request handling. Introduce UUID-based wallet ID generation and update validation logic to ensure proper session management. Refactor configuration management to apply default values and validate required fields, enhancing overall robustness.
…ement request and validation logic for signing operations, including participant management and session handling. Enhance client functionality with detailed error logging and timeout management for improved reliability.
… signing examples to use hex decoding for public keys. Enhance error messages in coordinator validation logic for better clarity. Improve logging in cosigner runtime to include identity public key in startup messages.
…cosigners. Include configuration details, run order, and troubleshooting steps for coordinator, relay, and cosigner nodes.
…and various source files. This change ensures consistency in the usage of the mpcium-sdk across the project.
…ls on directory structure and `go.mod` replace directive for seamless integration of the SDK during local development.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 30450280 | Triggered | Generic High Entropy Secret | d36a786 | coordinator.config.yaml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Introduce composable runtime startup with optional gRPC orchestration transport, extend coordinator config/runtime plumbing, and support dual-protocol keygen result aggregation in coordinator state handling. Made-with: Cursor
Allow the coordinator client and example flows to submit keygen/sign requests and await results over gRPC while keeping NATS transport compatibility and adding dedicated gRPC client tests. Made-with: Cursor
Clarify that gRPC is used for client orchestration while participant transport, control fan-out, and session/result messaging remain on NATS and relay paths. Made-with: Cursor
Enhance the sessionToProtoResult function to include ECDSA and EdDSA public keys in the gRPC response. Update the coordinator client to decode and return these keys in the session result structure, improving the key sharing capabilities of the client.
Enhance coordinator dual-protocol keygen flow to reuse existing wallet protocol keys, publish a stable aggregate result, and expand integration-style tests for gRPC and NATS request/result behavior. Made-with: Cursor
Protect session transitions with operation-level locking and buffer peer MPC packets that arrive before local party startup, then flush them safely when MPC begins. Made-with: Cursor
Trim and normalize protocol values in NATS/gRPC keygen requests, add transport-level coverage for empty and "both" protocol inputs, and update the keygen example to use NATS aggregated key output. Made-with: Cursor
…structure. Update related functions and tests to accommodate changes from KeyShare to Keygen, ensuring consistency across the codebase.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
2 participants
No description provided.